Add satellite flavor for downstream deployments#628
Conversation
2d6d362 to
cd76c02
Compare
| - foreman | ||
| - katello |
There was a problem hiding this comment.
foreman-proxy feature can be added to this list
There was a problem hiding this comment.
as with hammer, I think that is something people should be actively opt in for?
content distribution to external proxies works without the feature, so in many architectures it won't be needed
There was a problem hiding this comment.
for now I do not have foreman-proxy enabled by default.
There was a problem hiding this comment.
I think it should be identical to what we've currently with rpm based installations and we should have similar features pre-enabled on satellite deploy for existing users, where foreman-proxy and hammer are enabled by default
@ekohl @vijay8451 wdyt?
91b2b95 to
08d9a70
Compare
|
tested the most recent version and that worked as well 😄 |
| help: Base flavor to use in this deployment. | ||
| choices: | ||
| - katello | ||
| - satellite |
There was a problem hiding this comment.
IMHO a Satellite user should not be able to select Katello, and a Katello user not Satellite
But we don't need to solve this right now
The satellite flavor provides a feature set matching what RPM-based Satellite ships by default, enabling proper downstream test coverage with foremanctl. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
08d9a70 to
93e0c81
Compare
Summary
satelliteflavor (src/vars/flavors/satellite.yml) with the feature set for Satellite deploymentskatelloflavor: dropscontent/debandcontent/python, adds features that Satellite ships by defaultDetails
The
theme-satellitefeature requires a corresponding entry infeatures.yaml(orfeatures.d/) to take effect. Without one, it is silently ignored.Usage:
Test plan
--flavor satelliteon a CentOS 9 VM — all features resolved, 0 failuresforemanctl featuresshows correct enabled/available featureshammer ping— all services healthy🤖 Generated with Claude Code